home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
PC Media 4
/
PC MEDIA CD04.iso
/
share
/
os2
/
teldr000
/
status.doc
< prev
next >
Wrap
Text File
|
1994-06-24
|
3KB
|
80 lines
The current feature list of Telnet Door as of version 0.00 is:
Binary mode supported (send and receive).
Sysop can take over from the user.
Uses IBM's TCP/IP system.
Can be operated as a simple telnet program (if you don't like IBM's telnet).
Supports logging all output to a file.
Multi-threaded and uses no polling.
32 bit.
Uses practically no CPU time, it should run 8 high speed lines on a 386 easily.
Supports running a debug file which can be used to give me information on
errors that occur on your system and of features in TELNET daemons on remote
systems which aren't yet supported by my program.
Current bug list is:
Doesn't support domain names. You must know the IP address of the
destination to telnet there. This will be fixed in the next version.
Some of the enhanced VT100 terminal settings don't work in local mode, due
to differences between OS/2's ANSI terminal and VT100. Everything works fine
for the remote end as long as they have a VT100 terminal.
Telnet Door automatically sets the terminal type to VT-100 if the
DORINFO1.DEF specifies ANSI graphics. This is the only teminal type that is
currently supported. However it does use all binary transmission so after
telnetting in to the remote system you will be able to change the terminal
type appropriately (IE the initial login prompt may not be displayed properly,
but after logging in you can use the TERM environment variable and "stty" to
change things after that).
My Linux system defaults to the "stty" setting "-opost" which means that it
sends bare line-feeds without carriage return characters when I login to it.
So after logging in it is necessary to run "stty opost" to correct this. If
you are the system administrator of the system you are using my program to
login to then making "stty opost" the first line of your "/etc/profile" file
should solve this (it worked for me).
Planned features are:
Sysop chat mode.
To write my own emulating library for VT100/VT200.
Directly support VT100/VT200 terminal emulations in all ways.
Supporting function keys via doorway mode.
Using TELNET controls for environment settings and all terminal settings.
Another program that I am thinking of writing in future (depending on
financial incentives) is a terminal server for OS/2. This would be a single
program that would control a lot of modems (could easily handle 16 lines and
probably 32 or even 64 if the right serial hardware was in place). I believe
that an OS/2 system running a well written multi-threaded terminal server
would give the same performance as an expensive proprietary terminal server.
Also an OS/2 system would probably be cheaper (a 386 with 8 megs of RAM running
in text mode with a small hard drive would handle 16 lines easily and should
cost less than a dedicated terminal server).
If you would like to see such a program written then let me know.